Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Annotation Explores the feasibility of using techniques such as program transformation and program abstraction to re-engineer and extend the life of an existing IT system. The authors (De Montfort University) outline a program transformation-based evolution workbench called FermaT, the architecture of the wide spectrum language (WSL), and a process for evolving object-oriented, real-time, and parallel systems. The final chapter presents six case studies that use FermaT and re- engineering assistant tools to evolve from source code to specifications or to new source code in a different language. Annotation copyrighted by Book News, Inc., Portland, OR.

Software maintenance. --- Software reengineering. --- Computer software reengineering --- Reengineering of software --- Software renewal --- Software renovation --- Software engineering --- Software maintenance --- Computer program maintenance --- Computer programs --- Computer software --- Maintenance, Software --- Software revision --- Computer programming --- Software reengineering --- Maintenance

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Empirical verification of knowledge is one of the foundations for developing any discipline. As far as software construction is concerned, the empirically verified knowledge is not only sparse but also not very widely disseminated among developers and researchers. This book aims to spread the idea of the importance of empirical knowledge in software development from a highly practical viewpoint. It has two goals: (1) Define the body of empirically validated knowledge in software development so as to advise practitioners on what methods or techniques have been empirically analysed and what the

Software engineering. --- Computer software. --- Software, Computer --- Computer systems --- Computer software engineering --- Engineering

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Design Methods for Reactive Systems describes methods and techniques for the design of software systems-particularly reactive software systems that engage in stimulus-response behavior. Such systems, which include information systems, workflow management systems, systems for e-commerce, production control systems, and embedded software, increasingly embody design aspects previously considered alone-such as complex information processing, non-trivial behavior, and communication between different components-aspects traditionally treated separately by classic software design methodologies. But, a

Computer software --- System design. --- Development.

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Information technology --- Web services --- Business enterprise --- Application software. --- Management Theory --- Management --- Business & Economics --- Application computer programs --- Application computer software --- Applications software --- Apps (Computer software) --- Computer software --- Application software --- Cloud computing --- Data processing

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk -- that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved.

Computer software --- Software failures. --- Risk management. --- Development. --- Failure of computer software --- Failures, Software --- Development of computer software --- Software development --- Failures --- Insurance --- Management --- Computer system failures --- Bugs, Software --- Software bugs --- Debugging in computer science --- COMPUTER SCIENCE/General --- BUSINESS/Business Technology --- Software-ontwikkeling.